Bump plugin version to v3.4.0 in deployment examples #419
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
almaslennikov
force-pushed
the
deployment-version
branch
from
1a7e25b
to
39df130
Compare
|
Hi @almaslennikov, i think its fine to bump the .yaml to last release like we did before (i.e bump to v3.4.0) we should first agree on this approach in a community meeting, there are a couple of issues around release proceess and image tag management:: |
almaslennikov
force-pushed
the
deployment-version
branch
from
39df130
to
8660ce9
Compare
almaslennikov
changed the title
|
@adrianchiris Let's bump it to the v3.4.0 now and discuss the transition to |
adrianchiris
approved these changes
Mar 29, 2022
|
@SchSeba @zshi-redhat could you please take a look on this PR once you have a time? |
|
LGTM |
zshi-redhat
approved these changes
Apr 7, 2022
|
Mellanox CI failed, shall we rerun? I cannot see the details of the CI job (404 not found). |
|
/retest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposal for the future:
Using a specific version of the plugin in deployment examples requires updating it for each release. This poses a risk of users
deploying an older version of the plugin than the specific one they checked out.
The proposal is to always use
latestand then in every release, update yaml for the release and upload it to the release page.